Further improve Variables manpage section#4864
Merged
Merged
Conversation
Tried to further clarify some details - how the default for a variable is handled (trying not to be too repetitive about the default for the default :-) ), and make more clear than an existing variables file is wiped out by writing to it with the Save() function. Signed-off-by: Mats Wichmann <mats@linux.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tried to further clarify some details - how the default for a variable is handled (trying not to be too repetitive about the default for the default :-) ), and make more clear than an existing variables file is wiped out by writing to it with the Save() function.
This is a doc-only change.
Contributor Checklist:
CHANGES.txtandRELEASE.txt(and read theREADME.rst).